Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1952

reference
31-tree-1
name
1952
tree-preservation-order

undefined

31-tpo-1
uprn
address-text
point
POINT (-0.951246 50.850755)
geometry
MULTIPOLYGON (((-0.951189 50.850748,-0.951191 50.850760,-0.951199 50.850770,-0.951212 50.850778,-0.951227 50.850783,-0.951245 50.850785,-0.951262 50.850783,-0.951278 50.850778,-0.951291 50.850771,-0.951299 50.850761,-0.951302 50.850749,-0.951300 50.850738,-0.951292 50.850728,-0.951280 50.850720,-0.951264 50.850715,-0.951246 50.850713,-0.951229 50.850715,-0.951213 50.850720,-0.951200 50.850727,-0.951192 50.850737,-0.951189 50.850748)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL